Billing Control - Data Verification
The Data Issues Tab provides a set of reports used to validate data in the TBS System. These reports are useful for helping clients review data prior to a production or Quick bill run and identify any issues that may need to be corrected prior to bill run.
These reports will run automatically during the Daily Billing process and report results. When triggered during Daily, the reports will check accounts across all billable billing cycles.
Additionally, these reports will be ran as part of the Test, Production and Quick billing processes. In these cases, the reports will only check accounts tied to the current Test / Production/ Quick bill run Schedule record.
The results can be filtered based on the level as well as exported to Excel, PDF or Word format.
These reports can be ran manually for a particular Schedule record by clicking the Run Data Verification button located on the Schedule tab. The results of these reports can be set up to run at a scheduled time and be emailed to a distribution group so that users are notified if there is any data that needs to be reviewed. Please work with your client solutions expert to set this up.
There are three levels or types of Data Issues:
- Error - must be fixed before billing can complete
- Warning - recommended to be fixed but will not impede the billing process
- Information - recommended to be reviewed to see if any data should be fixed
The system comes with a defined set of reports that are across all clients. Client specific Data Verification reports will be available from a tab labeled Additional Data Verification. The following describes the Standard set of Data Verification Reports:
| Category | Level | Report |
| Locations | Error | InCity flag cannot be null |
| Locations | Error | Postal Code must be valid for the country |
| Locations | Error | If the country requires state, state is required |
| Locations | Warning | If PCode isn't specific to a particular area (e.g., Federal taxes only) |
| Customers | Warning | Corp accounts with no sub accounts |
| Customers | Error | Disconnected Corp Account |
| Customers | Error | Duplicate Account Numbers |
| Customers | Error | Invalid Cycle |
| Customers | Warning | Invalid Email Bill Customers |
| Customers | Error | Mismatch CorpPaymentOption |
| Customers | Error | Missing Accounts in CustomerInformation |
| Customers | Error | Off-Cycle Corp/Sub Accounts |
| Customers | Error | Sub-Accounts that have a disconnected Corp Account |
| Customers | Error | Sub-Accounts With a Balance |
| Customers | Error | Sub-Account with Invalid Corp-Account |
| Products | Error | If the free plan type is corporate but account is not corporate |
| Products | Warning | Active Products on Disconnected Accounts |
| Products | Error | Invalid Locations on Products |
| Products | Warning | Misc Charges that have No Active Date |
| Details | Warning | Active Details on Disconnected Products |
| Details | Warning | Duplicate Activation Dates |
| Admin | Warning | Invalid Exception Codes |
| Call Records | Warning (based on Threshold Date)* | Threshold Report* |
*One noteworthy new data check looks for call records that have rating errors or are categorized as unassigned (cannot be found in TBS, but we have usage). The report will calculate based on the total number of CDRs processed in a previous month and report the percentage of errors / unassigned comparatively for the current month. Depending on the percentage of call records that have errors, one of the following issues is created:
- 0% - no message
- < 5% - Call record error percentage is 3.0% (1000 records).
- < 10% - Call record error percentage of 7.3% (12345 records) exceeds warning threshold.
- >= 10% - Call record error percentage of 11.3% (123445 records) exceeds error threshold.
- >= 10% with a new Threshold Date setting in the future: Call record error percentage of 11.8% (128921 records) would normally exceed the error threshold. However, until 05/06/2018, this is a warning instead of an error.
The Threshold Date can be set by a client's account manager for use during acquisitions, as it can take some time to catch up with these kinds of errors.